Improve logging in TrashedRegisterFinder.ProcessBlock #1284
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add some extra logging to help debug errors during analysis.
|
Thanks for the PR. I will probably make this a general tool for usage in the other transformations in the analysis stage. It will help with debugging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, nothing would appear in the event log for certain errors that occurred in
TrashedRegisterFinder.ProcessBlock(). Now, for any exception that is not handled elsewhere, a reference to the statement that caused the exception will be added to the log, and the containing block will be dumped.Code by @uxmal.